v0.0.80 - #297
Merged
Merged
v0.0.80#297
Conversation
devsuitup
enabled auto-merge (squash)
September 17, 2026 13:18
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version bump only —
package.json+package-lock.json, the same two files and three lines as every previous bump. Subject is exactlyv0.0.80so the release-notes step filters it out of the changelog, as it does forv0.0.79 (#289)and its predecessors.What ships in v0.0.80
Release notes for the manual publish
The workflow writes a bare subject dump and leaves the release a draft. Two things in this one need saying in prose — a silent behaviour change users will otherwise discover by finding files missing, and a freeze that was reachable without any hostile input. Suggested body for
gh release edit v0.0.80 --draft=false --latest --notes-file …:Order of operations
Per
README.md"Fork release-flow gotchas" — the tag has to come after this merges, and from an account with push rights onorigin:Tagging before the squash-merge would leave a tag that is not an ancestor of
main, and the release-notes step derives its range fromgit describe.